home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Freeware 2001 May
/
SGI Freeware 2001 May - Disc 1.iso
/
dist
/
fw_hylafax.idb
/
usr
/
freeware
/
man
/
cat4
/
pagermap.Z
/
pagermap
Wrap
Text File
|
2000-06-09
|
4KB
|
132 lines
PPPPAAAAGGGGEEEERRRRMMMMAAAAPPPP((((4444FFFF)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((MMMMaaaayyyy 8888,,,, 1111999999996666)))) PPPPAAAAGGGGEEEERRRRMMMMAAAAPPPP((((4444FFFF))))
NNNNAAAAMMMMEEEE
pagermap - SNPP pager identifier mapping file
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
The file eeeettttcccc////ppppaaaaggggeeeerrrrmmmmaaaapppp (by default) is used by the SNPP
support in _h_f_a_x_d(1M) to map pager identifiers specified with
the PAGE directive to IXO/TAP or SMS service providers and
optionally a Pager Identification Number (PIN). (The
ability to specify a PIN makes it possible to define _a_l_i_a_s_e_s
for pagers.) Note that eeeettttcccc////ppppaaaaggggeeeerrrrmmmmaaaapppp may be called a
different name; the filename is specified with the
_P_a_g_e_r_I_D_M_a_p_F_i_l_e configuration parameter read by _h_f_a_x_d(1M).
The pagermap file is comprised of one or more lines of the
following format:
<_p_a_t_t_e_r_n> <_d_i_a_l_s_t_r_i_n_g>[/<_p_i_n>]
Each line specifies a <_p_a_t_t_e_r_n> that is matched against a
client-specified pager identifier string. A pattern may be
a plain string or a POSIX 1003.2 extended regular
expression; plain strings must compare exactly while regular
expressions are unanchored and any substring match
constitutes a ``hit''. Regular expressions are
distinguished from plain strings by the presence of one or
more of the magic characters ``[]*.^$-+{}()''. The
<_d_i_a_l_s_t_r_i_n_g> identifies the IXO/TAP or SMS service provider
to contact for delivery or, if <_d_i_a_l_s_t_r_i_n_g> is the string
``reject'' (case insensitive) then the pager identifier is
rejected. If the optional <_p_i_n> is specified then it used
to deliver the page instead of the client-specified
identifier.
If the matching expression is a regular expression the
optional <_p_i_n> may reference the entire string matched by
the regular expression with the ``&'' character. Substrings
matched with the ``(...)'' constructs may be referenced by
using ``\_n'' where _n is a single numeric digit between 1 and
9 that refers to the _n-th matched substring; c.f.
_r_e__f_o_r_m_a_t(7), _s_e_d(1), etc.
_h_f_a_x_d processes lines in the mapping file sequentially; the
first line with a pattern that matches the pager identifier
is used to deliver or reject the page. Lines that begin
with a ``#'' are treated as comments and discarded. Leading
whitespace on a line is also ignored.
EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS
The following defines an alias for ``sam'', submits all
destinations with a leading ``Sky'' to a particular IXO/TAP
service provider, and otherwise rejects the pager ID. (Note
that using alphabetics in dial strings requires a dialstring
Page 1 (printed 3/21/00)
PPPPAAAAGGGGEEEERRRRMMMMAAAAPPPP((((4444FFFF)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((MMMMaaaayyyy 8888,,,, 1111999999996666)))) PPPPAAAAGGGGEEEERRRRMMMMAAAAPPPP((((4444FFFF))))
rules file that understands how to map alphabetics to key
codes-or one that passes them through verbatim.)
# a simple mapping example
sam 5551212/99
Sky(.*) 1800SkyTel/\1
.* reject
SSSSEEEEEEEE AAAALLLLSSSSOOOO
_h_f_a_x_d(1M), _h_y_l_a_f_a_x(4F)
Page 2 (printed 3/21/00)